Without a committment to code review workflows, this is meaningless.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 27 2022
Aug 13 2021
Aug 16 2017
Won't fix in favor of decentralisation.
Jul 13 2017
"gouttegd (Damien Goutte-Gattat)" <noreply@dev.gnupg.org> writes:
I've just pushed the two fixes. `GNUPGHOME` is now set to the tests directory when running the tests and `gpg-connect-agent` is now looked for in `PATH` at runtime. When the tests are run, Scute now contacts the agent intended for the tests instead of any agent running on behalf of the Jenkins user. And so the tests pass or skip appropriately.
Jul 12 2017
I've just pushed the two fixes. GNUPGHOME is now set to the tests directory when running the tests and gpg-connect-agent is now looked for in PATH at runtime.
Jul 11 2017
All build artifacts are accessible
I see several problems here:
All build artifacts are accessible, e.g.: https://jenkins.gnupg.org/job/scute/ws/XTARGET/native/obj/tests/test-suite.log
Jun 8 2017
Jun 7 2017
May 30 2017
May 8 2017
May 4 2017
In T3133#96706, @marcus wrote:I don't have the full picture here, but maybe this gives you some fresh ideas:
About problem 1: Am I understanding it correctly that all builds share an install tree that is continuiously updated by all builds in all projects (for the same flavor)?
I don't have the full picture here, but maybe this gives you some fresh ideas:
May 3 2017
May 2 2017
Apr 26 2017
gnupg/distcheck aborted in #1046 and #1047 with 5min timeout, but it takes more than 8min.
Please modify timeout for gnupg/distcheck.