#13295 closed task (fixed)
Release Trac 1.2.6
Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.2.6 |
Component: | general | Version: | |
Severity: | normal | Keywords: | release |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
1.2.6 has been targeted to June 20th.
I'm hoping this can be the last release on 1.2.x. If a major issue or security issue is found, we can reconsider another release.
Attachments (0)
Change History (7)
comment:1 by , 5 years ago
Type: | enhancement → task |
---|
comment:2 by , 5 years ago
Description: | modified (diff) |
---|
comment:3 by , 5 years ago
comment:5 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
follow-up: 7 comment:6 by , 4 years ago
The build had one job failure for Python 2.7 on PostgreSQL. Timezone issue?
I re-ran the job and it succeeded.
https://travis-ci.org/github/edgewall/trac/jobs/703750374
Not sure if it's worth investigating.
====================================================================== FAIL: test (trac.wiki.test.WikiTestCase) Test milestone: link resolver ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/travis/build/edgewall/trac/trac/wiki/test.py", line 133, in test % (msg, self.file, self.line, self.title, formatter.flavor)) AssertionError: ========== expected: ========== <p> <a class="missing milestone" href="/milestone/foo" rel="nofollow">milestone:foo</a> <a class="milestone" href="/milestone/boo" title="No date set">Milestone Boo</a> <a class="closed milestone" href="/milestone/roo" title="Completed 24 hours ago (Jun 30, 2020, 3:34:45 AM)">Milestone Roo</a> <a class="milestone" href="/milestone/woo" title="Due in 24 hours (Jul 2, 2020, 3:34:45 AM)">Milestone Woo</a> <a class="milestone" href="/milestone/zoo" title="24 hours late (Jun 30, 2020, 3:34:45 AM)">Milestone Zoo</a> </p> ========== actual: ========== <p> <a class="missing milestone" href="/milestone/foo" rel="nofollow">milestone:foo</a> <a class="milestone" href="/milestone/boo" title="No date set">Milestone Boo</a> <a class="closed milestone" href="/milestone/roo" title="Completed 23 hours ago (Jun 30, 2020, 3:34:45 AM)">Milestone Roo</a> <a class="milestone" href="/milestone/woo" title="Due in 25 hours (Jul 2, 2020, 3:34:45 AM)">Milestone Woo</a> <a class="milestone" href="/milestone/zoo" title="23 hours late (Jun 30, 2020, 3:34:45 AM)">Milestone Zoo</a> </p> ========== wiki: ========== u' milestone:foo [milestone:boo Milestone Boo] [milestone:roo Milestone Roo] [milestone:woo Milestone Woo] [milestone:zoo Milestone Zoo] ' ========== diff: ========== --- expected +++ actual @@ -1,8 +1,8 @@ <p> <a class="missing milestone" href="/milestone/foo" rel="nofollow">milestone:foo</a> <a class="milestone" href="/milestone/boo" title="No date set">Milestone Boo</a> -<a class="closed milestone" href="/milestone/roo" title="Completed 24 hours ago (Jun 30, 2020, 3:34:45 AM)">Milestone Roo</a> -<a class="milestone" href="/milestone/woo" title="Due in 24 hours (Jul 2, 2020, 3:34:45 AM)">Milestone Woo</a> -<a class="milestone" href="/milestone/zoo" title="24 hours late (Jun 30, 2020, 3:34:45 AM)">Milestone Zoo</a> +<a class="closed milestone" href="/milestone/roo" title="Completed 23 hours ago (Jun 30, 2020, 3:34:45 AM)">Milestone Roo</a> +<a class="milestone" href="/milestone/woo" title="Due in 25 hours (Jul 2, 2020, 3:34:45 AM)">Milestone Woo</a> +<a class="milestone" href="/milestone/zoo" title="23 hours late (Jun 30, 2020, 3:34:45 AM)">Milestone Zoo</a> </p> /Users/travis/build/edgewall/trac/trac/ticket/tests/wikisyntax.py:1: "milestone: link resolver" (default flavor) ---------------------------------------------------------------------- Ran 2228 tests in -1683.090s FAILED (failures=1)
comment:7 by , 4 years ago
Replying to Ryan J Ollos:
Ran 2228 tests in -1683.090s
The same issue of #13254. Perhaps, the system clock is adjusted in OSX VM.
It is reported in the following pages but seems to be not fixed.
I'll try to release weekend of June 27-28th, along with 1.0.20.