Menu
▾
▴
dpp-devel — [THIS LIST HAS BEEN MOVED TO GOOGLE GROUPS - "https://groups.google.com/forum/#!forum/saros-devel"] Developer List for Saros
This list is closed, nobody may subscribe to it.
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
|
Oct
(61) |
Nov
(88) |
Dec
(27) |
| 2010 |
Jan
(55) |
Feb
(93) |
Mar
(133) |
Apr
(148) |
May
(92) |
Jun
(56) |
Jul
(110) |
Aug
(28) |
Sep
(229) |
Oct
(93) |
Nov
(137) |
Dec
(91) |
| 2011 |
Jan
(62) |
Feb
(207) |
Mar
(157) |
Apr
(59) |
May
(122) |
Jun
(56) |
Jul
(105) |
Aug
(154) |
Sep
(64) |
Oct
(232) |
Nov
(224) |
Dec
(60) |
| 2012 |
Jan
(93) |
Feb
(251) |
Mar
(571) |
Apr
(205) |
May
(82) |
Jun
(48) |
Jul
(49) |
Aug
(34) |
Sep
(69) |
Oct
(22) |
Nov
(85) |
Dec
(41) |
| 2013 |
Jan
(30) |
Feb
(50) |
Mar
(66) |
Apr
(37) |
May
(11) |
Jun
(36) |
Jul
(40) |
Aug
(20) |
Sep
(9) |
Oct
(9) |
Nov
(28) |
Dec
(38) |
| 2014 |
Jan
(19) |
Feb
(20) |
Mar
(11) |
Apr
(5) |
May
(16) |
Jun
(26) |
Jul
(50) |
Aug
(60) |
Sep
(75) |
Oct
(49) |
Nov
(37) |
Dec
(9) |
| 2015 |
Jan
(20) |
Feb
(51) |
Mar
(72) |
Apr
(33) |
May
(22) |
Jun
(35) |
Jul
(38) |
Aug
(47) |
Sep
(48) |
Oct
(21) |
Nov
(47) |
Dec
(31) |
| 2016 |
Jan
(57) |
Feb
(42) |
Mar
(23) |
Apr
(21) |
May
(27) |
Jun
(9) |
Jul
(10) |
Aug
(43) |
Sep
(69) |
Oct
(30) |
Nov
(27) |
Dec
(34) |
| 2017 |
Jan
(34) |
Feb
(38) |
Mar
(35) |
Apr
(35) |
May
(40) |
Jun
(10) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <je...@sa...> - 2017-07-09 04:35:54
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2166/> |
|
From: <je...@sa...> - 2017-07-08 04:38:31
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2165/> |
|
From: <je...@sa...> - 2017-07-07 04:36:01
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2164/> |
|
From: Tobias B. <tob...@fu...> - 2017-07-04 17:22:31
|
Hi all, it was brought to my attention, that some subscribers of these lists might not be familiar with the Saros team. My apologies for any confusion that I might have caused. To clarify: In my previous mail, I was speaking on the behalf of the Saros team in general. The mentioned Franz is Franz Zieris (Fra...@fu...), the head of the Saros team. Best regards, Tobias Bouschen |
|
From: Tobias B. <tob...@fu...> - 2017-07-04 13:13:58
|
Hi all, after a discussion with Franz, we decided to leave the old SourceForge mailing list behind, as its technical administration grew more and more cumbersome over the years. We are moving this list to Google Groups. The new group is named "saros-devel" and is reachable through "https://groups.google.com/forum/#!forum/saros-devel". There are two options for subscribing to the new mailing list: 1.) With a googlemail account: If you are logged in with a googlemail account, you can use "http://groups.google.com/group/saros-devel/boxsubscribe" or go to "https://groups.google.com/forum/#!forum/saros-devel" and use the blue "Join group" button next to the group name. Through "My settings -> Membership and email settings", you can manage your username, email address used for the subscription and the email delivery preference (daily summaries, combined updates or updates for each message). 2.) Without a googlemail account: You can subscribe to the list via the web interface by going to "http://groups.google.com/group/saros-devel/boxsubscribe" and entering the email address you want to join with or via email by sending an email to "sar...@go..." (the subject or content of the mail does not matter). Either of those should result in an automated mail to the given address which contains a link to complete the joining process. This method does *NOT* allow you to change your settings. This means you will not be able to set a username. Instead, everything before the '@' in your address will be used ("fo...@st..." will result in the username "foo.bar"). Furthermore, you will not be able to change your subscription options, meaning that it is not possible to enable daily summaries or combined updates for the list. Best regards, Tobias |
|
From: <je...@sa...> - 2017-07-01 04:36:41
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2158/> |
|
From: Zieris, F. <Fra...@fu...> - 2017-06-30 10:21:16
|
Un-be-liev-able! Where is the champagne? -----Original Message----- From: je...@sa... [mailto:je...@sa...] Sent: Friday, June 30, 2017 6:36 AM To: dpp...@li... Subject: [DPP-Devel] Jenkins build is back to stable : Saros-Eclipse-STF-Nightly #2157 See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2157/> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ DPP-Devel mailing list DPP...@li... https://lists.sourceforge.net/lists/listinfo/dpp-devel |
|
From: <je...@sa...> - 2017-06-30 04:36:39
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2157/> |
|
From: Zieris, F. <Fra...@fu...> - 2017-06-19 08:40:57
|
At first glance, everything works fine now. Finally we got a Gerrit setup with the functionality of the old build-server and the responsiveness of the new one. Nice! Franz -----Original Message----- From: Tobias Bouschen [mailto:tob...@fu...] Sent: Monday, June 19, 2017 1:50 AM To: DPP...@li... Subject: [DPP-Devel] Gerrit database maintenance finished Hi all, as the title already suggests, the Gerrit database maintenance is finished. The autocomplete for names works now. The normal usage of Gerrit can resume. If you notice any errors while working with Gerrit, especially if you are still getting a "Server error 500" at any point or are noticing errors that you are sure weren't there before, it would be nice if you could share them with me. You can do this either directly or through this mailing list. Best regards, Tobias ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ DPP-Devel mailing list DPP...@li... https://lists.sourceforge.net/lists/listinfo/dpp-devel |
|
From: Tobias B. <tob...@fu...> - 2017-06-18 23:51:14
|
I just noticed that I forgot to reply to the mailing list instead of just Stefan. Here is my reply to his note about the accessibility of the STF-Tests: -------- Weitergeleitete Nachricht -------- Betreff: Re: [DPP-Devel] Reason for the missing reminders about Saros-Eclipse-STF-Nightly being unstable Datum: Tue, 13 Jun 2017 16:21:30 +0200 Von: Tobias Bouschen <tob...@fu...> An: Stefan Rossbach <sro...@ar...> The problem is that it is currently running on an old build server which is not open to the public. A move to the normal build server (saros-build) as well as the integration into the normal Jenkins instance is currently in the works. After this move, the STF-Test-Job as well as its logs (and errors) can be viewed through the normal Jenkins interface (http://saros-build.imp.fu-berlin.de/jenkins/). Am 13/06/2017 um 16:10 schrieb Stefan Rossbach: > The result of the regression is not available for developers outside of > the FU network. > > So there is no way to figure out what is going wrong unless you want to > spend about 45 minutes doing the regression by yourself. > > And as far as I remember the STF is not VIP. You can actually use it to > write tests. > > BR, > > Stefan > > > On 13.06.2017 16:01, Tobias Bouschen wrote: >> Hi everyone, >> >> I recently disabled the "unstable" notification for out automated >> Jenkins build of the Saros-Eclipse-STF-Nightly (the mails "[DPP-Devel] >> Jenkins build is still unstable: Saros-Eclipse-STF-Nightly #XXXX"). >> >> The underlying problem was not fixed, but the continuing reminders where >> not very helpful as it is not crucial to the project and there was >> nobody actively working on the problem. I will have a look at it in the >> near future. But in the meantime, this should not cause any problems for >> current users/developers as the STF is only a test framework (which is >> still a work in progress). >> >> My apologies for not announcing this sooner. >> >> Regards, >> Tobias >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> DPP-Devel mailing list >> DPP...@li... >> https://lists.sourceforge.net/lists/listinfo/dpp-devel |
|
From: Tobias B. <tob...@fu...> - 2017-06-18 23:49:56
|
Hi all, as the title already suggests, the Gerrit database maintenance is finished. The autocomplete for names works now. The normal usage of Gerrit can resume. If you notice any errors while working with Gerrit, especially if you are still getting a "Server error 500" at any point or are noticing errors that you are sure weren't there before, it would be nice if you could share them with me. You can do this either directly or through this mailing list. Best regards, Tobias |
|
From: Tobias B. <tob...@fu...> - 2017-06-18 12:59:59
|
Hi all, there are currently some problems with the encoding/collation of the database used by our Gerrit setup, which cause things like the autocomplete for usernames not to work. To fix these issues, I will have to make changes to the database. I am not quite sure which effects these changes will have on the availability of Gerrit. Furthermore, if major problems occur due to these changes, I will have to load a backup version of the database, meaning any changes made through Gerrit during this time could potentially be lost. This is why I would like to ask you to refrain from using Gerrit between 23:59 today and 02:00 tomorrow. I will send another mail when I'm done. Best regards, Tobias |
|
From: Stefan R. <sro...@ar...> - 2017-06-13 14:10:29
|
The result of the regression is not available for developers outside of the FU network. So there is no way to figure out what is going wrong unless you want to spend about 45 minutes doing the regression by yourself. And as far as I remember the STF is not VIP. You can actually use it to write tests. BR, Stefan On 13.06.2017 16:01, Tobias Bouschen wrote: > Hi everyone, > > I recently disabled the "unstable" notification for out automated > Jenkins build of the Saros-Eclipse-STF-Nightly (the mails "[DPP-Devel] > Jenkins build is still unstable: Saros-Eclipse-STF-Nightly #XXXX"). > > The underlying problem was not fixed, but the continuing reminders where > not very helpful as it is not crucial to the project and there was > nobody actively working on the problem. I will have a look at it in the > near future. But in the meantime, this should not cause any problems for > current users/developers as the STF is only a test framework (which is > still a work in progress). > > My apologies for not announcing this sooner. > > Regards, > Tobias > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > DPP-Devel mailing list > DPP...@li... > https://lists.sourceforge.net/lists/listinfo/dpp-devel |
|
From: Tobias B. <tob...@fu...> - 2017-06-13 14:01:55
|
Hi everyone, I recently disabled the "unstable" notification for out automated Jenkins build of the Saros-Eclipse-STF-Nightly (the mails "[DPP-Devel] Jenkins build is still unstable: Saros-Eclipse-STF-Nightly #XXXX"). The underlying problem was not fixed, but the continuing reminders where not very helpful as it is not crucial to the project and there was nobody actively working on the problem. I will have a look at it in the near future. But in the meantime, this should not cause any problems for current users/developers as the STF is only a test framework (which is still a work in progress). My apologies for not announcing this sooner. Regards, Tobias |
|
From: <je...@sa...> - 2017-06-02 04:38:01
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2134/> |
|
From: <je...@sa...> - 2017-06-01 04:38:15
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2133/> |
|
From: <je...@sa...> - 2017-05-31 04:37:51
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2132/> |
|
From: <je...@sa...> - 2017-05-30 04:38:37
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2131/> |
|
From: <je...@sa...> - 2017-05-29 04:38:22
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2130/> |
|
From: <je...@sa...> - 2017-05-28 04:37:38
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2129/> |
|
From: <je...@sa...> - 2017-05-27 04:37:56
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2128/> |
|
From: <je...@sa...> - 2017-05-26 04:37:49
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2127/> |
|
From: <je...@sa...> - 2017-05-25 04:37:44
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2126/> |
|
From: <je...@sa...> - 2017-05-24 04:37:22
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2125/> |
|
From: <je...@sa...> - 2017-05-23 04:37:56
|
See <http://saros-build-old.imp.fu-berlin.de/jenkins/job/Saros-Eclipse-STF-Nightly/2124/> |
253 messages has been excluded from this view by a project administrator.