Scenario | Bug Id | Description | Failures |
math_cexp_scenario | bug516_2(cexp) | The cexp() family of functions function shall compute the complex exponent of their argument. At the specified point the result of computing the exponent is very imprecise (inaccuracy is more then 20 bits from the end of the floating point number). |
failure 2
| 11 more... failure 3
failure 4
failure 5
failure 6
failure 7
failure 8
failure 9
failure 10
failure 11
failure 12
failure 13
|
math_cexp_scenario | bug516_2(cpow) | The cpow(x, y) family of functions shall compute the complex power function x^y, with a branch cut for the first parameter along the negative real axis. If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpow(x, y) return (-1) + (near)(1e-16) * i. This result is too far from (-1). If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpow(x, y) return (-1) - (near)(1e-16) * i. This result is too far from (-1). If the argument is x = (-1) + (-0) * i and y = (-1) + (-0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1). If the argument is x = (-1) + (0) * i and y = (-1) + (0) * i then the function cpowl(x, y) return (-1) + (near)(1e-20) * i. This result is too far from (-1). |
failure 14
| 3 more... failure 15
failure 16
failure 17
|
math_complex_scenario | bug841(cproj) | According to LSB, the cproj(z) family of functions shall compute a projection of z onto Riemann sphere: z projects to z except all complex infinities. The old implementation in glibc does a stereographic projection that contradicts the standard. |
failure 18
| 5 more... failure 19
failure 20
failure 21
failure 22
failure 23
|
math_rand_scenario | bug511_1(initstate) | The initstate() function handles restarting of random-number generator. One of the argument to initstate() function is size of the state array. The larger the state array, the more random the numbers. According to LSB, values for the amount of state information are 8, 32, 64, 128, and 256 bytes and if initstate() is called with size less than 8, it shall return NULL. But on the target machine the function doesn't return NULL when called with size less than 8. |
failure 24
| 2 more... failure 26
failure 28
|
math_rand_scenario | bug511_2(initstate) | The initstate() function handles restarting of random-number generator. According to LSB, upon successful completion, initstate() shall return a pointer to the previous state array; otherwise, a null pointer shall be returned. But on the target machine the function returns neither a pointer to the previous state, nor NULL pointer. |
failure 25
| 2 more... failure 27
failure 29
|
math_real_fdim_overflow_scenario | bug512(fdim) | The fdim(x, y) family of functions shall determine the positive difference between their arguments. According to LSB, if the result overflows then fdim() shall fail and shall set ERANGE error code. But on the target machine, the functions set error code EOK instead of ERANGE when overflow occurs. |
failure 30
| 2 more... failure 31
failure 32
|
ncurses_misc_scenario | bug357(keyname) | The keyname() function generates a character string whose value describes the key specified as the argument of the functions. The meta-character notation in function keyname() from ncurses library, when running it with meta-character parameter, shall be used only if meta-characters are enabled (according to the LSB standard). But it is used irrespectively of enabling of meta-characters. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0357. |
failure 33
| 127 more... failure 34
failure 35
failure 36
failure 37
failure 38
failure 39
failure 40
failure 41
failure 42
failure 43
failure 44
failure 45
failure 46
failure 47
failure 48
failure 49
failure 50
failure 51
failure 52
failure 53
failure 54
failure 55
failure 56
failure 57
failure 58
failure 59
failure 60
failure 61
failure 62
failure 63
failure 64
failure 65
failure 66
failure 67
failure 68
failure 69
failure 70
failure 71
failure 72
failure 73
failure 74
failure 75
failure 76
failure 77
failure 78
failure 79
failure 80
failure 81
failure 82
failure 83
failure 84
failure 85
failure 86
failure 87
failure 88
failure 89
failure 90
failure 91
failure 92
failure 93
failure 94
failure 95
failure 96
failure 97
failure 98
failure 99
failure 100
failure 101
failure 102
failure 103
failure 104
failure 105
failure 106
failure 107
failure 108
failure 109
failure 110
failure 111
failure 112
failure 113
failure 114
failure 115
failure 116
failure 117
failure 118
failure 119
failure 120
failure 121
failure 122
failure 123
failure 124
failure 125
failure 126
failure 127
failure 128
failure 129
failure 130
failure 131
failure 132
failure 133
failure 134
failure 135
failure 136
failure 137
failure 138
failure 139
failure 140
failure 141
failure 142
failure 143
failure 144
failure 145
failure 146
failure 147
failure 148
failure 149
failure 150
failure 151
failure 152
failure 153
failure 154
failure 155
failure 156
failure 157
failure 158
failure 159
failure 160
|
ncurses_move_scenario | bug313(mvcur) | According to LSB, if screen position (newrow, newcol) is not a valid address for the terminal in use, mvcur(int xpos, int ypos) function call to this cursor position should fail (mvcur() is the function from Ncurses library that moves the cursor), but error doesn't occur on inputs (-1000000, -1000000), (10000000, 10000000). Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0313. |
failure 161
| 1 more... failure 162
|
ncurses_slk_label_scenario | bug342(slk_label) | Upon successful completion, slk_label(labnum) function from ncurses library returns the requested label with number labnum with leading and trailing blanks stripped. But on the target machine there are outputs with unstripped blanks. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0342. |
failure 163
|
ncurses_string_scanf_scenario | bug524_1(scanw) | According to the standard, upon successful completion, scanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function scanw() returned 1 when it is called with first argument " %i". Bug was added to linuxtesting.ru as bug number S0524. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 164
| 5 more... failure 165
failure 166
failure 167
failure 168
failure 169
|
ncurses_string_scanf_scenario | bug524_2(vw_scanw) | According to the standard, upon successful completion, vw_scanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function vw_scanw() returned 1 when it is called with first argument " %i". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 188
| 5 more... failure 189
failure 190
failure 191
failure 192
failure 193
|
ncurses_string_scanf_scenario | bug524_3(vwscanw) | According to the standard, upon successful completion, vwscanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function vwscanw() returned 1 when it is called with first argument " %i". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 194
| 5 more... failure 195
failure 196
failure 197
failure 198
failure 199
|
ncurses_string_scanf_scenario | bug524_4(mvwscanw) | According to the standard, upon successful completion, mvwscanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function mvwscanw() returned 1 when it is called with fmt argument " %i". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 182
| 5 more... failure 183
failure 184
failure 185
failure 186
failure 187
|
ncurses_string_scanf_scenario | bug524_5(mvscanw) | According to the standard, upon successful completion, mvscanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function mvscanw() returned 1 when it is called with fmt argument " %i". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 170
| 5 more... failure 171
failure 172
failure 173
failure 174
failure 175
|
ncurses_string_scanf_scenario | bug524_6(wscanw) | According to the standard, upon successful completion, wscanw() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). But on the target machine, the function wscanw() returned 1 when it is called with fmt argument " %i". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0524. |
failure 176
| 5 more... failure 177
failure 178
failure 179
failure 180
failure 181
|
ncurses_terminal_termcap_simple_scenario | bug686(tgetnum) | According to the standard, upon successful completion, tgetnum() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). RETURN VALUE ... Upon successful completion, functions that return an integer return OK. Otherwise, they return ERR. But the real implementation does not match LSB standard. Manual pages for GNU extension, that is used in real Linux systems, say: The tgetnum routine gets the numeric entry for id, or -1 if it is not available. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0686. |
failure 200
|
ncurses_terminal_termcap_simple_scenario | bug687(tgetflag) | According to the standard, upon successful completion, tgetflag() function from Ncurses library shall return OK(0), otherwise, it shall return ERR(-1). RETURN VALUE ... Upon successful completion, functions that return an integer return OK. Otherwise, they return ERR. But the real implementation does not match LSB standard. Manual pages for GNU extension, that is used in real Linux systems, say: The tgetflag routine gets the boolean entry for id, or zero if it is not available. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0687. |
failure 201
|
process_meta_user_scenario | bug102(setuid) | The setuid() function sets the real user ID, effective user ID, and the saved set-user-ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real user ID or the saved set-user-ID, setuid() shall set the effective user ID to this value. But on the target machine setuid() fails when trying to set the effective user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 225
| 1 more... failure 226
|
process_meta_user_scenario | bug103(setreuid) | The setreuid() function shall set the real and effective user IDs of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the saved set-user-ID, setreuid() shall always be successful to set the real user ID to this value. But on the target machine setreuid() fails when trying to set the real user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 223
| 1 more... failure 224
|
process_meta_user_scenario | bug104(setgid) | The setgid() function sets the real group ID, effective group ID, and the saved set-group-ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real group ID or the saved set-group-ID, setgid() shall set the effective group ID to this value. But on the target machine setgid() fails when trying to set the effective group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 207
| 1 more... failure 208
|
process_meta_user_scenario | bug106(setregid) | The setregid() function shall set the real and effective group IDs of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the saved set-group-ID, setregid() shall always be successful to set the real group ID to this value. But on the target machine setregid() fails when trying to set the real group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 209
| 13 more... failure 210
failure 211
failure 212
failure 213
failure 214
failure 215
failure 216
failure 217
failure 218
failure 219
failure 220
failure 221
failure 222
|
process_meta_user_scenario | bug82(seteuid) | The seteuid() function sets the effective user ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real user ID or the saved set-user-ID, or if the process has appropriate privileges, seteuid() shall set the effective user ID to this value. But on the target machine seteuid() fails when trying to set effective user ID to the saved set-user-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 205
| 1 more... failure 206
|
process_meta_user_scenario | bug83(setegid) | The setegid() function sets the effective group ID of the calling process to the value, specified as its argument. According to LSB, if this argument equals to the real group ID or the saved set-group-ID, or if the process has appropriate privileges, setegid() shall set the effective group ID to this value. But on the target machine setegid() fails when trying to set effective group ID to the saved set-group-ID value. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0102. |
failure 203
| 1 more... failure 204
|
process_resources_ulimit_priviledged_scenario | bug794(ulimit) | It is a test suite deficiency that will be fixed soon. |
failure 228
|
process_resources_ulimit_unpriviledged_scenario | bug794(ulimit) | It is a test suite deficiency that will be fixed soon. |
failure 229
|
process_scheduler_scenario | bug504(sched_setscheduler) | The sched_setscheduler() function shall set the scheduling policy and scheduling parameters of the specified process. According to LSB, upon successful completion, the function shall return the former scheduling policy of the specified process. But it always returns 0 on the target machine. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0504. |
failure 230
| 15 more... failure 231
failure 232
failure 233
failure 234
failure 235
failure 236
failure 237
failure 238
failure 239
failure 240
failure 241
failure 242
failure 243
failure 244
failure 245
|
signal_sigstr_basic_scenario | bug685(strsignal) | If sig is not a valid signal number, strsignal shall return either a pointer either a pointer to the string "unknown signal", or a null pointer. SYNOPSIS ... char * strsignal(int sig); ... RETURN VALUE If sig is a valid signal number, strsignal() shall return a pointer to the appropriate description string. Otherwise, strsignal() shall return either a pointer to the string "unknown signal", or a null pointer. ... But in real, strsignal return "Unknown signal", a space, and a number sig. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0685. |
failure 246
|
time_conversion_scenario | bug379(asctime_r) | The asctime_r() function converts date and time to a string and returns it. According to LSB, if the function is unsuccessful, it should return NULL, But on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. |
failure 248
| 1 more... failure 249
|
time_conversion_scenario | bug380(asctime) | The asctime() function converts date and time to a string and returns it. According to LSB, if the function is unsuccessful, it should return NULL, But on the target machine it returns a string with '?' symbols, for example "??? Oct 9 09:09:09 1909". Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0379. |
failure 247
|
time_time_scenario | bug377(stime) | The stime() function shall set the system's idea of the time and date to the time referenced by function argument. According to LSB, if this argument is NULL then stime() shall set error code to EINVAL. But it sets error code to EFAULT instead of EINVAL. The bug was fixed in libc 2.4. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0377. |
failure 272
| 8 more... failure 273
failure 274
failure 275
failure 276
failure 277
failure 278
failure 279
failure 280
|
util_assert_errx_scenario | bug488(errx) | The errx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 281
| 8 more... failure 282
failure 283
failure 284
failure 285
failure 286
failure 287
failure 288
failure 289
|
util_assert_verrx_scenario | bug489(verrx) | The verrx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 290
| 8 more... failure 291
failure 292
failure 293
failure 294
failure 295
failure 296
failure 297
failure 298
|
util_assert_warnx_scenario | bug486(warnx) | The warnx() function shall display a formatted error message on the standard error stream. According to LSB, the formatted error message, the last component of the program name, a colon character, a space and a newline character shall be output. But on the target machine colon character, and a space are not output after the formatted error message. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0488. |
failure 299
| 199 more... failure 300
failure 301
failure 302
failure 303
failure 304
failure 305
failure 306
failure 307
failure 308
failure 309
failure 310
failure 311
failure 312
failure 313
failure 314
failure 315
failure 316
failure 317
failure 318
failure 319
failure 320
failure 321
failure 322
failure 323
failure 324
failure 325
failure 326
failure 327
failure 328
failure 329
failure 330
failure 331
failure 332
failure 333
failure 334
failure 335
failure 336
failure 337
failure 338
failure 339
failure 340
failure 341
failure 342
failure 343
failure 344
failure 345
failure 346
failure 347
failure 348
failure 349
failure 350
failure 351
failure 352
failure 353
failure 354
failure 355
failure 356
failure 357
failure 358
failure 359
failure 360
failure 361
failure 362
failure 363
failure 364
failure 365
failure 366
failure 367
failure 368
failure 369
failure 370
failure 371
failure 372
failure 373
failure 374
failure 375
failure 376
failure 377
failure 378
failure 379
failure 380
failure 381
failure 382
failure 383
failure 384
failure 385
failure 386
failure 387
failure 388
failure 389
failure 390
failure 391
failure 392
failure 393
failure 394
failure 395
failure 396
failure 397
failure 398
failure 399
failure 400
failure 401
failure 402
failure 403
failure 404
failure 405
failure 406
failure 407
failure 408
failure 409
failure 410
failure 411
failure 412
failure 413
failure 414
failure 415
failure 416
failure 417
failure 418
failure 419
failure 420
failure 421
failure 422
failure 423
failure 424
failure 425
failure 426
failure 427
failure 428
failure 429
failure 430
failure 431
failure 432
failure 433
failure 434
failure 435
failure 436
failure 437
failure 438
failure 439
failure 440
failure 441
failure 442
failure 443
failure 444
failure 445
failure 446
failure 447
failure 448
failure 449
failure 450
failure 451
failure 452
failure 453
failure 454
failure 455
failure 456
failure 457
failure 458
failure 459
failure 460
failure 461
failure 462
failure 463
failure 464
failure 465
failure 466
failure 467
failure 468
failure 469
failure 470
failure 471
failure 472
failure 473
failure 474
failure 475
failure 476
failure 477
failure 478
failure 479
failure 480
failure 481
failure 482
failure 483
failure 484
failure 485
failure 486
failure 487
failure 488
failure 489
failure 490
failure 491
failure 492
failure 493
failure 494
failure 495
failure 496
failure 497
failure 498
|
util_compress_scenario | bug844(gzputc) | According to LSB, the gzputc() function shall write the single character c, converted from integer to unsigned character. On success, gzputc() shall return the value written, but it returns initial argument. |
failure 499
|
util_format_time_scenario | bug803(getdate) | The requirement claims: "Extra whitespace in either the template file or in string shall be ignored." But if there are any white spaces at the end of the query, the function returns with error 7. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0803. |
failure 502
|
util_format_time_scenario | bug808(strptime) | Values of all fields of struct tm shall be positive or 0. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0808. |
failure 505
|
util_format_time_scenario | bug810(strptime) | The char *strptime(const char *restrict buf, const char *restrict format, struct tm *restrict tm); function shall convert the character string pointed to by buf to values which are stored in the tm structure pointed to by tm, using the format specified by format. The <time.h> header shall declare the structure tm, which shall include at least the following members: int tm_sec Seconds [0,60]. int tm_min Minutes [0,59]. int tm_hour Hour [0,23]. int tm_mday Day of month [1,31]. int tm_mon Month of year [0,11]. int tm_year Years since 1900. int tm_wday Day of week [0,6] (Sunday =0). int tm_yday Day of year [0,365]. int tm_isdst Daylight Savings flag. Function strptime can not rigth work with some input data. If buf = "0 Sun 2006" and format = "%U %a %Y" then strptime must find first Sunday in first week (Sunday as the first day of the week) 2006 year. 2006 year begins with Sunday. But after call to strptime tm.tm_yday = -7. if buf = "0 Mon 2007" and format = "%W %a %Y" then strptime must find first Monday in first week (Monday as the first day of the week) 2007 year. 2007 year begins with Monday. But after call to strptime tm.tm_yday = -7. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0810. |
failure 503
| 1 more... failure 504
|
util_format_wprintf_swprintf_scenario | bug505(swprintf) | According to LSB, on error swprintf() function shall return -1 and set errno global variable. On the target machine, swprintf() function returns -1, but doesn't set error code in errno global variable. This contradicts LSB standard for this function. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. |
failure 507
|
util_format_wprintf_vswprintf_scenario | bug506(vswprintf) | According to LSB, on error vswprintf() function shall return -1 and set errno global variable. On the target machine, vswprintf() function returns -1, but doesn't set error code in errno global variable. This contradicts LSB standard for this function. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0505. |
failure 508
|
util_format_wtime_scenario | bug561(wcsftime) | %z Replaced by the offset from UTC in the ISO 8601:2000 standard format, or by no characters if no timezone is determinable; depending on the field tm_isdst in tm structure. But on the target machine it is detected incorrect processing of this conversion pattern when tm_isdst is set to a positive number - no daylight savings time offset is used. Additional information about this bug may be found at http://linuxtesting.org/results/report?num=S0561. |
failure 509
|