Opened 21 months ago

Last modified 13 months ago

#24043 reopened defect

monotonic time test failure on 0.3.0.x

Reported by: weasel Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.3.0.12
Severity: Normal Keywords: 034-triage-20180328, 034-removed-20180328, 031-unreached-backport
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

https://jenkins.torproject.org/job/tor-debian-0.3.0-nightly-binaries/169/ARCHITECTURE=amd64,SUITE=jessie/consoleFull

on (I think) 4d73ed10c40938d1ef1cf5628fd1840ee64df8ff

01:45:40 util/pwdb: [forking] OK
01:45:40 util/calloc_check: OK
01:45:40 util/monotonic_time: 
01:45:40   FAIL ../src/test/test_util.c:5552: assert(monotime_coarse_diff_msec(&mtc1, &mtc2) OP_GE 125): 0 vs 125
01:45:40   [monotonic_time FAILED]
01:45:40 util/monotonic_time_ratchet: [forking] OK
01:45:40 util/htonll: OK

Child Tickets

Attachments (1)

consoleText (790.4 KB) - added by weasel 20 months ago.
build log

Download all attachments as: .zip

Change History (13)

comment:1 Changed 21 months ago by nickm

Keywords: 031-backport 030-backport added
Milestone: Tor: 0.3.2.x-final

comment:2 Changed 21 months ago by dgoulet

Status: newneeds_information

That jenkins link is dead unfortunately. And I see this is not failing anymore so do we consider it fixed or we should wait for it until release of 032?

comment:3 Changed 21 months ago by nickm

It's probably an intermittent thing, if it's happening.

comment:4 Changed 20 months ago by nickm

Resolution: worksforme
Status: needs_informationclosed

comment:5 Changed 20 months ago by weasel

Resolution: worksforme
Status: closedreopened

reopening, it's still happening, and that's a problem because it fails our build pipelines on releases.

Changed 20 months ago by weasel

Attachment: consoleText added

build log

comment:6 Changed 20 months ago by dgoulet

Speaking of monotonic time failing, #23696 is getting that on Windows 7 that is a monotonic get failure. Not sure if related but noting it.

comment:7 Changed 18 months ago by nickm

Keywords: 030-backport removed

Remove 030-backport from all open tickets that have it: 0.3.0 is now deprecated.

comment:8 Changed 17 months ago by teor

Milestone: Tor: 0.3.2.x-finalTor: 0.3.4.x-final

These feature and bugfix tickets have no patches. The earliest they will get done is 0.3.4.

comment:9 Changed 16 months ago by nickm

Keywords: 034-triage-20180328 added

comment:10 Changed 16 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:11 Changed 15 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

comment:12 Changed 13 months ago by teor

Keywords: 031-unreached-backport added; 031-backport removed

0.3.1 is end of life, there are no more backports.
Tagging with 031-unreached-backport instead.

Note: See TracTickets for help on using tickets.